Memory management? Like garbage collection? I'm confused how you can thread processing differently than memory management. I mean, imagine the cache-misses that will be created when a different thread on a different core is jerking around with the memory you are trying to use. In other words, you can't command a memory-write on a separate thread if the processing that follows is dependent on the memory being written to.
If they are just talking about defragging and garbage collection, the compiler should already thread that out separately. Its not the programmers fault if the compiler injects memory management code right in the middle of their execution.
[citation][nom]Exodite2[/nom]Manual memory management? That's so... 1960s.[/citation]
Oh brother, that's whats wrong with computer programming today, too many kids growing up on Java. Believe it or not, some mission-critical applications can't just leave it up to the compiler to figure out what to do with memory. Not that Word processors are ever mission critical, I'm just saying proper memory management and being aware of the effects of your memory usage are still good ideas.