Row events in statement based binlog: optimization possible?

--source include/have_binlog_format_statement.inc

CREATE TEMPORARY TABLE tt1 (c INT);

INSERT INTO tt1 VALUES (1);

CREATE TEMPORARY TABLE tt2 (c INT PRIMARY KEY);

INSERT tt2 VALUES (1),(2);

--error ER_DUP_ENTRY

UPDATE tt2, tt1 SET tt2.c=2;

CREATE TABLE t1 (c INT);

INSERT t1 SELECT * FROM tt2;

SHOW BINLOG EVENTS;

# Cleanup

DROP TABLE tt1, tt2, t1;

...

master-bin.000001	1243	Annotate_rows	1	0	INSERT t1 SELECT * FROM tt2

master-bin.000001	1293	Table_map	1	0	table_id: 32 (test.t1)

master-bin.000001	1338	Write_rows_v1	1	0	table_id: 32 flags: STMT_END_F

mariadb-test$ ../bin/mariadb-binlog --base64-output=decode-rows -vvv var/mysqld.1/data/master-bin.00[0-9][0-9][0-9][0-9] | grep '^###'

### INSERT INTO `test`.`t1`

### SET

###   @1=1 /* INT meta=0 nullable=1 is_null=0 */

### INSERT INTO `test`.`t1`

### SET

###   @1=2 /* INT meta=0 nullable=1 is_null=0 */