The anonymous block, select from dual example is fixed for next beta.
I went through your activity stream on Toad World and from what I can tell the only outstanding issue (other than CI’s inability to locate table refs in some SQL due to syntax errors) is this one for common table expressions. http://www.toadworld.com/products/toad-for-oracle/toad_for_oracle_beta_program/f/86/t/27672 This is logged.
What other context sensitive issues are you seeing? In general Code Insight should allow what is appropriate given the clause. Some restrictions have been recently lifted, but some are still in place. For example, if you invoke CI after “INSERT INTO |” it will limit shown objects to TABLE, VIEW, SCHEMA, and SYNONYM since other object types don’t make much sense there. If invoking after “INSERT INTO my_table (fld1, fld2, |)” then only columns are shown, etc.
Context sensitive issues can boil down to one of 2 causes… a) error in the logic that sets item visibility based on context or b) a bug that prevents CI from properly identifying the clause you’re working on or tables referenced in SQL. In case A the info is available, but hidden from you. These are easy fixes. In case B the info is not even available to show. The most likely cause is B and fixes here can be simple or more complicated depending on the source of the issue (Toad or parser).
If I’ve missed any of your reports please point me to them or post samples and I’ll investigate.