Off the top of my head, I would say this would be trivial to do. But you may not write your code the way I write mine ;-).

package My::App;
use base 'CGI::Application';
use DBI;
#...

sub _connect
{
  my $self = shift;
  my $dbh = $self->param('dbh');
  return $dbh if $dbh;

  my $dsn = $self->param('dsn');
  # user, password...
  $dbh = DBI->connect($dsn, ...);
  $self->param('dbh' => $dbh);
  $dbh;
}

sub _prepare
{
  my $self = shift;
  my $dbh  = $self->_connect();
  $dbh->prepare(@_);
}

sub _execute
{
  my $self = shift;
  my $sth  = shift;
  $self->{_execute}++; # here it is...
  $sth->execute(@_);
}
[download]

I route all my DBI calls through functions like these simply to save time and effort later when (not if) I want to do something wierd. For example, passing in specific parameters to the prepare, or, in your case, counting the executions. You can even put some calls to Time::HiRes around that execute and total up the time for the queries that way.

I also like delaying my connections until I really need them. That way, if a given mode doesn't need to touch the database, then I don't waste time, cycles, or whatever, in creating that connection. Not only am I lazy, but so are my programs ;-)