You are probably thinking of DCOM, COM+ and ActiveX.
COM is simply a set of standards and rulesets to implement and interface language agonistic objects, and it hasn’t been fully replaced by .NET in all regards yet.
It’s rather old but hasn’t been deprecated nor it will be in the near future according to MS, and .NET really only replaced parts of the whole lot, but the general idea of COM components is still alive.
To you as a programmer that it uses COM or .NET doesn’t make that much difference, since the API largely abstracts it anyway, and if you want to create your own lower level constructs you’d end up using the C++ API that (luckily) doesn’t require any COM or .NET crap.
The COM compliance is all on Soft’s side and of little to no consequence when you script. What I’m not that sure about is how much of the C# support was added with pure .NET and how much with the (limited) subset of things that are compatible between both .NET and COM.
What is your concern exactly?