If you wield the power, then I propose that you create a "date" table in your database. I find having a "date" table extremely useful for memorializing (and centralizing) certain attributes regarding dates as well as these types of needs (even if it involves a, wait for it, triangular join).
Creating the date table ...
It's pretty straight forward and feel free to load it up with columns, even if they are something that can be computed using native SQL Server functions. Having them physically stored sometimes provides more flexibility as well as a performance boost.
create table Dt (
Dt date primary key clustered,
BestDayEverBit bit not null default(0));
insert Dt (Dt)
select top (100000)
dateadd(day, (row_number() over (order by (select null))), convert(date, '1900'))
from sys.all_columns a
cross join sys.all_columns b;
The query ...
declare
@BegDt date = '2016-02-03',
@EndDt date = '2016-02-13';
select *
from Dt
where Dt >= @BegDt
and Dt < @EndDt;
Results
Dt BestDayEverBit
---------- --------------
2016-02-03 0
2016-02-04 0
2016-02-05 0
2016-02-06 0
2016-02-07 0
2016-02-08 0
2016-02-09 0
2016-02-10 0
2016-02-11 0
2016-02-12 0
Hope this helps.