Better error handling for long running queries in exported CSV

While it's somewhat helpful to show PHP errors in line on a browsed page. It's entirely devoid of that context when an exported CSV shows this error:

"<b>Fatal error</b>: Maximum execution time of 60 seconds exceeded in <b>/../sites/all/modules/civicrm/CRM/Utils/Array.php</b> on line <b>52</b><br />"

Due to large data sets being processed for our data sets, the exporter moves along happily till the maximum execution time is reached. Sadly this error gets pushed up into the CSV along with any contact records that had been retrieved.

It would be great if rather then placing the error inside the CSV, the user could be alerted that their query was costly and informed to limit their result set.

I noticed this particular case with the SYBUNT Report.