Atomic<Type>::memoryBarrier() could be factored out

The implementations of Atomic::memoryBarrier() don’t depend on the template arguments and could be moved outside the template.

Yes, that’s true… But I wanted to put it in that class so that all the atomic stuff is kept in the same place, and if I was looking for a memory barrier, that’s the first place I’d go to look for it. I didn’t really want to have a loose global function floating around as well.