This is a follow up to the post that I made concerning a possible memory
leak in SQLDataReader().

I have finally narrowed down the cause.  The managed C++ thread that was
using the DataReader had made a call to CoInitialize() because it formally
used straight ADO before I converted it to ADO.NET.  When I comment out the
CoInitialize() call, the memory leak appears to no longer occur.

Now, my question is why does ADO.NET SQLDataReader appear to leak memory if
CoInitialize() is called on the thread that is using it?  This could be a
problem if I need to utilize other COM objects on the thread that is using
ADO.NET in managed C++.

How to use bind variables effectively for Sql performance?
Regarding Connection object behaviour
Saving DataTable as XML
ADO.NET 2.0 & MSDE & Win98
TimeStamp field, help needed