2) Fix tracking of OWN_hung in Win32 CS lock manager (lock-up debugging aid)
3) Fix possible unsynchronized access to memory manager in Win32 CS builds
and client library. Have shown itself as a very rare crash of Win32 CS manager
process during its startup.
4) Reduce warnings a little
Points 2 and 3 need to be backported to B1_5_Release
Right now locks.h is used by the memory manager only. In its internals you
can find that SS uses Spinlock class whilst CS uses SharedSpinlock (which is
just a dummy now). So I think everything except SharedSpinlock should be
#ifdef'ed with SUPERSERVER in locks.h. The only doubt I have is a SOLARIS
check there (is it related to SS or CS?).
