time.{h,cpp} -> worldtime.{h,cpp}

why? because posix. you'd think that i wouldn't need to worry about ever
conflicting with anything, because I'd be at my own include path, right?
apparently not, as i did just that on some persons system (and somehow
not my own??!). which really makes me wonder what's a more scaleable solution
than "rename the conflict to something not".

asking everyone i know, looking around basically everywhere, leads
people who either never heard of the issue, think that < > vs "" includes
will somehow fix it (even though i know which to use properly and when),
or that setting the include prefix will help, and gcc docs say it
may or may not be listened to anyways.

seems that everybody just works around it via a case by case rename.
one could do e.g. ore_timer.h, etc....but seems a bit silly. surely
i'm overlooking something? how can any of this scale? there's got to be
a million people installing something like mytimer.h, or object.h...
or matrix.h...and it's all got to conflict, doesn't it?

only tangible results i got were from the haxe guys, who have/had the
same problem and apparently resolved it via this commit-esque