No, it's an implicit commit. I just got the same results. I ran this query against Adventureworks:

SELECT soh.[SalesOrderID]

,sod.[SalesOrderDetailID]

FROM Sales.[SalesOrderHeader] soh

INNER JOIN [Sales].[SalesOrderDetail] sod

ON soh.[SalesOrderID] = sod.[SalesOrderID]

I captured the batch and the statement. In the example, the statement had CPU = 16 and the batch had CPU = 31. The batch, I believe (I've looked at the documentation and can't find anything supporting that or denying it), simply includes all the time & cost to commit of the query where as the statement only has the minimal entries for the statement. Regardless, I would only use the statements if you had particular issues within a procedure or batch that you couldn't identify without having the full set of statements. The batch or rpc call events usually have all the data you need.