Time conditions in reports are inaccurate at the "right" endpoint

Currently, we are using a closed time interval, which is inclusive of the endpoints. Since the time input field does not give second accuracy, it is impossible to make the rightmost endpoint either inclusive (for example, <= 235959) or exclusive (< 000000), so when running sequential reports using times we will always have uncounted records, or double-counted records.

The easiest solution would be to add 59 seconds to the "to" time. This still puts the burden on report designers to know that the end time should be one minute earlier than the desired end of the period.