|You don't need to investigate it. It's been well discussed and documented already.
Read here, http://getdotnetco.web119.discountasp.net/GdncStore/free/Articles/The%20Memory%20Mystery.htm[^] and the other links I gave you last time.
.net memory is not something you need to worry about. Just trust the CLR. Unless you are doing some serious, cutting edge, right on the metal, hardcore processing, the CLR is efficient enough for you.
Rather than measuring things like memory usage, measure things like perceived performance. If your app starts up quick enough, and responds to user clicks fast enough, why do you care about how much memory it is using. Just let the CLR handle itself.
Instead, learn how to write efficient and optimal code within the CLR environment. Learn about the dispose pattern, learn how to manage your resources and learn about the pros/cons of the different data types, structs and class, and the passing semantics (by ref/by value etc)