For purposes of closing out my original questions for this thread,
conclusions are inline below.

On Fri, Sep 11, 2020 at 05:54:16PM -0400, David T. Lewis wrote:
> 
> This leads me to ask three questions:
> 
> 1) Does #eventMillisecondClock need to exist? It looks like it might be
> a kludge, if so could we make it go away?
> 

No, eventMillisecondClock does not need to exist. Following recent updates
in trunk, it is no longer used for anything related to event time stamps.


> 2) If the eventMillisecondClock method does need to exist, should it be changed
> to retrieve a millisecond value that is aligned with that of the events?
> 

No. See above. No change is needed.


> 3) If not 2) then do we need to change the Windows VM to somehow use event
> timestamps that match eventMillisecondClock?
> 

No. Event timestamps from the VM do not need to match eventMillisecondClock.
The VM does not need to be fixed.

Dave