select  count(1)
from    temp bs
where   status in(1, 7, 8, 19 )


PLAN_TABLE_OUTPUT

Plan hash value: 2768968421
 
---------------------------------------------------------------------------------------------
| Id  | Operation          | Name                   | Rows  | Bytes | Cost (%CPU)| Time     |
---------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT   |                        |     1 |     3 | 15877   (1)| 00:00:01 |
|   1 |  SORT AGGREGATE    |                        |     1 |     3 |            |          |
|   2 |   INLIST ITERATOR  |                        |       |       |            |          |
|*  3 |    INDEX RANGE SCAN|         OPT_IX         |   484M|  1385M| 15877   (1)| 00:00:01 |
---------------------------------------------------------------------------------------------
 
Predicate Information (identified by operation id):
---------------------------------------------------
 
   3 - access("STATUS"=1 OR "STATUS"=7 OR "STATUS"=8 OR 
              "STATUS"=19)

how many rows are in the table?
how many rows does your query actually fetch?

select count(*) from temp bs;
select count(*) from temp bs where status in(1, 7, 8, 19 );

1. if you are fetching 484 million rows from a table that has 484 million /.02 (2% Rule) rows, then use an index, otherwise do a table scan.  PRECISION STYLE VS. WAREHOUSE STYLE.
2. if your table is partitioned on status then do a table scan to exploit partition pruning.  PRECISION STYLE TURNED INTO WAREHOUSE STYLE.
3. if your table is not partitioned on status then slap someone and ask why not.  STUPIDITY TUNING.
4. if your table has an index on status then see if multiple index range scans help.  DEJA VU.  (this is in fact what you are doing currently but in the end it really goes back to #1).
5. as was suggested, look at a covering index as an option if there are not a lot of columns being fetched.  BIG BILLY GOAT GRUFF TO THE CBO.