Most kernellish interfaces have switched from milliseconds to nanoseconds,
and we can use them in-memory at no extra cost, even if all current formats
are limited to at most 1μs precision.

(WIP as I'm unsure if this move is worth the confusion.)

It reduces clarity by making code less readable.  There's a reason we write
a sum of products a*b+c*d not (a*b)+(c*d); bitwise products being similar.

Mostly to shut up the warning spam, we don't care either way.

Just to silence the warning: building for Windows requires a POSIX
environment like msys anyway.

Matters only if we have a compressor without a matching decompressor or vice
versa.

Exploitable!

The max width should be taken from libtty, but I don't care about win32
so much, this code needs to be replaced anyway.

Can't access the sysmenu under Wine.

No security impact -- our struct continues well past this buffer, with no
sensitive data in the next two ints.

Otherwise, they trigger random unrelated commands.

We heavily use object-oriented code.