Based on that query you aren't looking at range_scan_count or singleton_lookup_count so it looks like you don't know if this index is used by selects. I prefer to look at sys.dm_db_index_usage_stats. I wouldn't consider dropping the index on the basis of the current information that you have provided.

I wouldn't recommend running profiler against a production server as it has a negative performance impact. You can define the trace using profiler, script it, and run it as a server-side trace, which has a much lower impact on the server.