I see that Jonathan Lewis mentioned the ADVANCED format and the OUTLINE format in a blog article a couple of years ago:
http://jonathanlewis.wordpress.com/2008/03/06/dbms_xplan3/

Thanks for bringing that format parameter to my attention.

Sorry to hear about your test DB being corrupted. Table T1 is the same table T1 found at the start of Chapter 8 of the Expert Oracle Practices book. The table is fairly large, and the index has such a high clustering factor that it only makes sense to use the index for very small percentages of the table (say less than 0.06% of the table). I wanted to see what impact parallel query would have on the speed of the full table scan.

The good news is that once you have the table T1 built you will be able to test that section of the book to see if a lower buffer cache hit ratio may be better than a higher buffer cache hit ratio.

I am not sure why it is not documented and where I found it before but using ADVANCED instead of ‘ALLSTATS LAST +PEEKED_BINDS +PROJECTION +ALIAS +PREDICATE +COST +BYTES’) gives the same result.

SELECT * FROM table(DBMS_XPLAN.DISPLAY_CURSOR((‘&sql_id’),&child_number,’Advanced’))

You can also use – operator like Advanced -PEEKED_BINDS which is easier than ++++ and –
Is there anything you know and can add about Advanced ?

I could not try the second bit yet to comment about because your initial test case made my test DB corrupted, which I can only deal tomorrow (I missed the 1 hour warning:))

Is there any specific reason for you to create that big table ?

Thanks for the great overview, examples and compilation of this very basic but important Oracle function.