Air carrier descending into DCA on the ELDEE 4 STAR missed crossing restriction; Controller reports numerous similar events.

Narrative

While flying the ELDEE 4 arrival; we were held high due to traffic. Later we were cleared to descend via the ELDEE 4 arrival. We placed 8000 FT in the altitude window as per the ELDEE 4 and I increased our descent rate using vertical speed in an effort to catch up to the descent profile. Approximately 4 miles west of REVUE; I realized I had descended through the crossing altitude at REVUE of 15;000 FT and leveled the aircraft out approximately 700 FT low. As I leveled the aircraft out; ATC reminded us about the crossing at REVUE and said there was no traffic conflict. We rejoined the descent profile on the ELDEE 4 arrival. We were in a high workload environment getting new ATIS calling company and doing the In-Range checklist. While this is not the cause of the altitude crossing deviation; it was probably a contributing factor. I was using vertical speed in an effort to catch up with the descent profile and I did not go back to the profile mode. In the future; I need to make sure all crossing restrictions are met; no matter which descent mode I am in. We should get ATIS and do the In-Range checklist and company calls as early as possible. Supplemental information from ACN 827720: I was working a radar/feeder sector at Potomac TRACON. I cleared Aircraft X to descend via the ELDEE 4 arrival. The procedure is charted to cross REVUE waypoint at 15;000 FT. Aircraft X descended early (into the airspace of another sector below mine) and crossed REVUE at 13;800 FT. This scenario repeats on a daily basis by a variety of aircraft types and airline companies. It would be nice if the FAA would devote some attention to these repeated events before something more serious than a pilot deviation happens.