With binary logging on, now upgrading civicrm is impossible

Binary logging is a know issue when you want special features like multilingual sites or have civicrm logging.
The only solution is to have SUPER privilege or use the "log_bin_trust_function_creators variable".
A SUPER privilege is impossible when you take security serious.
Even "log_bin_trust_function_creators" has downsides. I trust civicrm to be able to handle log_bin_trust_function_creators safely, but...
This variable can only be set on DB Server level, so you also need to trust ALL other apps on the same level.

That is why we choose NOT to use mulitilingual or extended logging on our servers with binary logging on.

Unfortunately now even upgrading a civicrm gives the same warning:

[Error: Upgrade DB to 4.2.5: SQL]
DROP TRIGGER IF EXISTS civicrm_acl_before_insert [nativecode=1419 ** You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)]

What I know about these triggers is that they are only needed when multilingual settings and logging is ON. Can they be checked when Upgrading, so normal CiviCRM usage is still possible when you have Binary Logging on without the log_bin_trust_function_creators variable?

If that is not possible please update the requirements check, and warn before upgrades take place.