Hunting Memory Leaks, best practices?

Hi,

I started a new Thread because this Title makes more sense.

What are your best strategies to hunt down MemoryLeaks, especialls on Android? How can I check if a certain object get's relased? Does it make sense to include a Debug.WriteLine into the Destructor of the Class of interest?

Does it make sense to call GC.Collect to see if memory stays constant?

Thanks for all help!

Best
Thomas