Consumes are restored in DiLepton code, conflict is resolved

Checked on 
CMSSW_7_2_X_2014-07-01-0200
And everything looks ok.
In line 387, you allocate something with new. in line 391 you return in case `!event.getByToken(elecs_, elecs)`, and if I understand correctly the object in elecSelect is leaked.