Which is better multiple filtered traces or one trace on SQL Server 2000?

Question

I have a requirement to identify Active databases on a SQL Server 2000 cluster. There are 295 databases but the field has been narrowed to 60 databases that we are unsure if they are still in use.

I intend to use SQL Trace [sp_trace_create] and the Audit Login event to identify which databases are still in use.

My question is should I create multiple traces and filter for each database I am interested in, say 10 at a time?

Or, would 1 trace capturing all Audit Login events for all database which I can inspect later for only the databases I am interested be better.

I am measuring "better" here as less operational performance impact.

Thanks all.