Not really. Over at sysinternalls, there are some tools with code, to show you how to view how processes have a loaded copy of a DLL. To get at a COM object of a DLL you need to be in the process to see them, in which case you can then hazard a guess at how many times the DLL has been locked, but then each COM object created adds a lock, so you can't be sure which. I don't think COM was designed with these kind of metrics in mind.
"Je pense, donc je mange." - Rene Descartes 1689 - Just before his mother put his tea on the table. Shameless Plug - Distributed Database Transactions in .NET using COM+
