Fix infinite loop with LogPrint on Windows
Fix infinite loop with LogPrint on Windows

Running -printtodebugger -debug (or -debug=lock),
compiled with -DDEBUG_LOCKORDER would infinite loop
on Windows because every critical section lock/unlock
triggers a LogPrint.

Solution is to use the raw boost mutex instead of a CCriticalSection.

dooglus/clams,Jheguy2/Mercury,Kefkius/clams,Jheguy2/Mercury,robvanmieghem/clams,thunderrabbit/clams,thunderrabbit/clams,dooglus/clams,thunderrabbit/clams,robvanmieghem/clams,dooglus/clams,robvanmieghem/clams,Jheguy2/Mercury,nochowderforyou/clams,robvanmieghem/clams,dooglus/clams,Kefkius/clams,nochowderforyou/clams,dooglus/clams,Jheguy2/Mercury,robvanmieghem/clams,Kefkius/clams,nochowderforyou/clams,nochowderforyou/clams,Kefkius/clams,thunderrabbit/clams,Jheguy2/Mercury,nochowderforyou/clams,thunderrabbit/clams,Kefkius/clams