>> No, this question would not come up since I decided NOT to use the 24:00:00 but rather 23:59:59.
Is this for dbfs or SQL Server? If SQL Server or there's ever a possibility of upsizing, watch out for field types: SQL Server offers several datetimes with differing "ticks" that still can cost you the last second of the day if 23:59:59 is your upper limit.
A robust solution is not to use BETWEEN, but >= and <, with the upper bound set to 00:00:00 the next day. That captures all possible ticks between 23:59:59 and midnight.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
