QMap<Key,T> + T::operator& = bad things

QMap in its current form cannot be reliably used with any class (as either key or value) that implements operator&. This is because node_create (but also operator->) takes the address of a QMap::Node member when invoking placement operator new, which results in

, when invoking the class operator& is clearly not desired.

I discovered this with QMap, but other containers are likely affected. The fix is to use something like boost addressof instead of '&'.

The attached program /may/ demonstrate the problem; on my system I get a glibc-detected memory corruption (and the program hangs), but no errors from valgrind. (In my real program, however, the data access pattern causes the QMap storage to be filled with old data that causes a SEGV; this example is unfortunately not sophisticated enough to cause that.)