Hibernate isn't actually able to do that since it uses prepared statements all the time (as it's much more efficient), and keeping this context around for logging would complicate things significantly.
This is a limitation of the JDBC design, what people usually do during development is to use special JDBC drivers.. search the web for "jdbc spy", "P6Spy", or have a look into
http://code.google.com/p/log4jdbc/they should all be easy to setup and nicely separated, so you're sure you won't miss anything as Hibernate can't possible escape that ;)