Not something many .net programmers I know worry about, I've found recently though it's definitely worth spending some time monitoring the way the CLR reclaims memory from managed resources returning it to the managed heap during an applications execution. Slight code changes can give big performance benefits as CLR garbage collection happens on it's own thread, monitoring it is a simple process. The Windows tool Perfmon.exe has a nice trick up its sleeve whereby you can add performance counters...