No, nothing planned. Don't think it should go into the Orm either, you can start/close/rollback transactions with the DB class. Allowing the Orm to do the same would suggest it's a different type of transaction while the Orm would just use the DB as well, creating possible conflicts.
Bottom line: use the DB class to work with transactions and feel free have the Orm run queries during those transactions.