Commented Unassigned: Access violation errors after Anniversary Update [10616]

After the Windows 10 Anniversary Update (1607), I get access violation errors with Visual Leak Detector.

Exception thrown at 0x00007FF8A7B97FE7 (ntdll.dll) in Animator4_64.exe: 0xC0000005: Access violation reading location 0x00007FF8A7CD5252.

Module Information on ntdll.dll:
10.0.14393.0 (rs1_release.160715-1616)

I think, it's this line (during base member initialization):
QApplication(argc, argv)

I'm not experienced with VLD. I just started using it few days ago. But it worked fine until the Windows update, so it might be a good guess.
Comments: I can confirm same problem with 64bit build. Call stack prior to main: > ntdll.dll!RtlAllocateMemoryZone() Unknown 0000000000000001() Unknown 000000d87e7ff4b0() Unknown 000000d87e7ff030() Unknown ntdll.dll!LdrpInitializeNode() Unknown ntdll.dll!LdrpInitializeGraphRecurse() Unknown ntdll.dll!LdrpInitializeGraphRecurse() Unknown ntdll.dll!LdrpInitializeGraphRecurse() Unknown ntdll.dll!LdrpInitializeProcess() Unknown ntdll.dll!_LdrpInitialize() Unknown ntdll.dll!LdrInitializeThunk() Unknown 32bit builds are fine.