I believe this was incorrect before -- the value's length is 8, but the encoded length is 4.  Comments elsewhere assert that the bug causing incorrect lengths predated ms-resolution timestamps, so my code doesn't try and fix up this case.