View with renamed column does not use index

Question

Is there any reason why a view that renames the columns presented to the users would ignore an index?
For example:
CREATE OR REPLACE VIEW ENROLLMENT
(ENROLLMENT_ID, ENROLLMENT_DATE, FIRST_NAME)
AS
select distinct
a.col1 as enrollment_id,
a.col2 as enrollment_date,
a.col3 as first_name
from t1 a
When a user queries the view, with a WHERE FIRST_NAME = 'TOM", it results in a FTS. However, if you run the query against the base table (using col1, col2, and col3), it uses the index against t1 on (col3, col2, col1).

Answer 1

Well, I tried to create the supporting evidence afterwards (sigh, why do I keep doing that ...), it seems that Oracle has addressed this problem already:
SQL> create table t1
  2  as
  3  select l col1, sysdate - l/86400 col2, decode(l,1,'TOM',to_char(l)) col3
  4    from (select level l from dual connect by level <= 100000)
  5  /
Tabel is aangemaakt.
SQL> create index i1 on t1 (col3, col2, col1)
  2  /
Index is aangemaakt.
SQL> exec dbms_stats.gather_table_stats(user,'T1',method_opt=>'FOR ALL INDEXED COLUMNS')
PL/SQL-procedure is geslaagd.
SQL> create view enrollment
  2  (enrollment_id, enrollment_date, first_name)
  3  as
  4  select distinct
  5  a.col1 as enrollment_id,
  6  a.col2 as enrollment_date,
  7  a.col3 as first_name
  8  from t1 a
  9  /
View is aangemaakt.
SQL> set autotrace on explain
SQL> select * from enrollment where first_name = 'TOM'
  2  /
                         ENROLLMENT_ID ENROLLMENT_DATE     FIRST_NAME
                                     1 16-01-2007 14:41:25 TOM
1 rij is geselecteerd.
Uitvoeringspan
   0      SELECT STATEMENT Optimizer=CHOOSE (Cost=3 Card=1 Bytes=44)
   1    0   VIEW OF 'ENROLLMENT' (Cost=3 Card=1 Bytes=44)
   2    1     SORT (UNIQUE NOSORT) (Cost=3 Card=1 Bytes=18)
   3    2       INDEX (RANGE SCAN) OF 'I1' (NON-UNIQUE) (Cost=3 Card=1
           Bytes=18)I'm on 9.2.0.7.0 here, what's your version ?
Regards,
Rob.