> It's not making the limit check and the primitive call "atomic", it's > making the allocation and the primitive call "atomic". Whoops. You're right. I was thinking that because it will almost always be a variable sized allocation, the limit check will stay right there, but that's not necessarily true.