I agree that people need to call Apple support and let them know about this problem, when i talked to them they acted like they've never heard of this problem. We all know its a well documented problem, but they don't.
Despite calling apple support 3 times, and even going in store, they didn't replace my machine. i guess it was too long past the 2 weeks (i ordered it may 18), and i ordered it custom built online. I am having them repair it.
I too was worried about not being able to replicate the problem in store, but i quickly remembered the trick i saw here, with the two terminal windows open at the same time and running the command yes > /dev/null in both. Then checking the cpu on the activity moniter. Works like a charm. Apparantly it makes the cpu run at 100% on both cores. The genius, seeing this ran a bunch of cpu intensive programs (itunes visualizer, 3-d graphing, etc), hoping to max out the cpu. Once again, after checking the cpu on activity moniter, it shut down. It seems as though, running the cpu at max trigers it.
Don't ignore the problem like I did, hoping that some simple software fix will take care of it. It just makes you more past the 2 week window.
Also, anyone interested in a letter writing campaign, or website? i'm pretty ticked that they acted like this was no big deal. it's a new computer for christ's sake. They shouldn't just give us a repair number and act like this is standard procedure...not on a new machine. I'd understand this treatment by apple if this machine where a year old, but not 1.5 months old.
Sorry for the rant..