Well, consider a stack of dishes, you put new ones on top, and remove the
topmost ones when you need them.
This is how the cpu uses the its stack, First In, Last Out. I'm not sure
how the framework stack works, or if it is a conventional stack at all.
The heap is just that, a bunch of memory, items are stored at the first
available spot, but the position may change based on deletion of earlier
objects. The framework tries to keep all the used memory in one place so
new memory allocation can be speeded up.
This article may clarify some of it:
http://www.msdnaa.net/Resources/Display.aspx?ResID=601
--
Using M2, Opera's revolutionary e-mail client:
http://www.opera.com/m2/