Namespace design for data access layer?

Currently my data access layer namespace is organized like so: 


 


// contains code that provide CRUD operations and custom exceptions
MyCompany.MyProject.DataAccessLayer;
// contains custom business entities
MyCompany.MyProject.DataAccessLayer.Entities;

I'm thinking about separating the exceptions into a separate namespace like so: 


// contains custom exceptions
MyCompany.MyProject.DataAccessLayer.Exceptions;  
On the other hand, that means now I'll often need to add three using statements to consumers of the DAL and I'm a lazy typer.  So then I thought, why don't ...