I've been playing around with utlbstat.sql/utlestat.sql, only briefly I should add, for a short section on the history of Oracle's performance tuning utilities and I noticed a couple of things that tickled me enough to blog about them.
First, as the scripts output the comments, I noticed that quite a few of the updates to these scripts have been made by familiar names. Here are a few examples I've snipped out.
SQL> Rem cdialeri 01/02/01 - 891059: SQL*Plus compat, 1566460: connect /
SQL> Rem khailey 03/15/99 - 594266: Correct per logon stats, add fstat fields
SQL> Rem akolk 08/09/96 - #387757: fix latch hitratios
SQL> Rem drady 09/09/93 - merge changes from branch 1.1.312.2
Oak Table Network members, all. So, there you go, another possible path to membership is to have worked on bstat/estat

Then I noticed a bug in the scripts as supplied with 10.2.0.4! (Not sure I have to be that specific about the version here) The fact that the 10g version of V$SESSION contains wait event information leads to the following bug.
SQL> insert into stats$begin_bck_event
2 select event, sum(total_waits), sum(time_waited)
3 from v$session s, v$session_event e
4 where type = 'BACKGROUND' and s.sid = e.sid
5 group by event;
group by event
*
ERROR at line 5:
ORA-00918: column ambiguously definedDo you think I should file a bug report? I wonder what priority 10g bstat/estat bug-fixes have?

So, just to be clear, it's a bit of fun. I think you probably have better tools available these days! It's also very likely that I could lead a more varied and stimulating life if I put my mind to it