Logon Monitor Inaccurate for Windows 10?

Anyone else notice that the VMware Logon Monitor is fairly inaccurate in Windows 10 when comparing what the monitor reports to a stopwatch?

For example the logon monitor reports somewhere around 30 - 40 seconds yet a stopwatch shows that the logon is more towards the 60 - 75 seconds. We have a legal message domain policy that gives us a good point in Windows to start timing the logon process.

Using the Fling in the past on Windows 7 or Windows 10 LTSB the monitor was pretty accurate to +/- 3 seconds I would say.