I'm not out to throw stones at the Time library
Yup, no problem. I was just wondering whether you had a better "mousetrap"
This code in Time.cpp, in particular, gives me the willies
I think what the now() code is doing is waiting for the internal time to change to the next second before returning the time value. That way if it returns a string saying it is (for example) 17:15:12, the seconds value will have just "ticked" and be very close to 12.00 secs rather than being 12.85 or 12.13 or ....
It also doesn't have date/time string parsing
True, but I have always found it easy to parse the year, month, day, etc, of a string into the elements of the tm_elements structure and then just convert that to a time_t.