You could consider using a stored procedure! Or if the statements are meant to execute as one transaction, manage the transaction in your application's service layer.
With that in mind, if you need to execute multiple SQL statements in one DataMapper <statement> with Oracle using MS OracleClient or ODP.NET 10g, try wrapping those statements in a BEGIN...END; PL/SQL block.
<statement id="DeleteAccount" parameterClass="Account"> BEGIN DELETE FROM ORDERS WHERE ACCOUNT_ID = #Id#; DELETE FROM ACCOUNTS WHERE ACCOUNT_ID = #Id#; END; </statement>

I have found that wrapping the DDL within an anonymous PL/SQL block definitely works. However, I was wondering if anyone has tried the <iterate> tag within a <statement> tag. Specifically, I'd like to use the DataMapper config file to persist data from a complex Java object graph. This is similar to how the resultClass can be populated from a complex query (e.g., using the select= construct) but this isn't available for the <insert> tag.