I’m sorry for the inconvenience: unfortunately this looks like a bug we’re going to have to address in a future release. We realize it’s pretty important and so have prioritized it – but please note the very next release is in the final stages of preparation (and is subject to a code freeze) so it will realistically be the following release before we can address this.
In the meantime, could you workaround this perhaps by adding an explanatory note in the event description that it continues until midnight?
Thanks again for reporting this – and our apologies for any disruption.