My benchmark:

1) .net app, one text field, one button; private bytes 22mb, working set 27mb

2) native app, two text fields, three buttons; private bytes 1.2mb, working set 7.3mb

They're heavily tuned but I think having the generational hypothesis and copying longer-lived objects is still standard? As is allowing a fair amount of garbage to accumulate to increase throughput and reduce copying at the cost of memory footprint?

Posting instead of researching in hopes someone smarter can chime in, because I'm lazy.