Fix bad assumption about clock speed in MonoTime unit tests.

This code worked just fine so long as the two subsequent calls to
MonoTime.currTime returned different results, but apparently, some
machines, CPUs are fast enough in comparison to their system clock that
that's not guaranteed, so the diff was 0 instead of at least 1, and the
test failed. And looking at it, it probably should have been >= rather
than > anyway (at least based on the variable name - min).

This should make it so that the tests stop failing on Daniel Murphy's
machine.
When allocating a struct with "new", do not pass the pointer type info to the runtime, but the struct type info.
The fix also provides a small performance improvement as it no longer calls the virtual function TypeInfo.next() multiple times
Merge pull request #941 from rainers/fix_13404

Issue 13404 - heap-allocating a struct passes TypeInfo_Pointer to the GC, not TypeInfo_struct
Merge pull request #943 from jmdavis/time

Fix bad assumption about clock speed in MonoTime unit tests.
13377 - include core/sys/posix/syslog.d
Fix property enforcement in `core.time`.
Merge pull request #946 from denis-sh/fix-property-enforcement-in-`core.time`

Fix property enforcement in `core.time`.
Issue 13414 - Static destructors not called correctly with dynamic loading

Patch provided by Niklas Wallén in private correspondence.
Merge pull request #947 from klickverbot/run-tls-dtors

Issue 13414 - Static destructors not called correctly with dynamic loading
regression test for issue 13414
include syslog in windows builds
Merge pull request #948 from MartinNowak/test13414

regression test for issue 13414
Merge pull request #945 from klamonte/master

13377 - include core/sys/posix/syslog.d