Apple has shown through the software and APIs I've used that they aren't all 'A's. This is just Jobs having spewed his normal visionary talk. It makes for great conversation and something that is nice to consider, and having a goal of hiring someone great is awesome. There is nothing wrong with continuing to utilize his vision to promote good of some sort.
But, I have enough experience to know that there are no 'A' developers that stay that way. People burn out, lose drive, get kids, get sleep apnea, go though a mid-life crisis, and get tired. So, unless you are firing the old 'A's, they will be 'B's then 'C's, etc.
Also, hiring 'A's is incredibly difficult. If you don't have an 'A' company, 'A' benefits, an 'A' location or offer full-time telecommuting, 'A' tools, and 'A' staff working on 'A' products/projects, then if you think you got an 'A', you probably didn't. And you can be 'C' and hire an 'A' and that 'A', if he or she stays, will atrophy and become a 'B', 'C', or worse. 'A's need to be motivated by their work just like anyone else. Jony Ives said recently that what he is working on now is what he is most proud of. He didn't say that because he is an 'A', and because he is inherently motivated on his own and could do that for a 'C' company. For a 'C' company, his work might have been shit and he might have been likely to piss on his designs, because of the bureaucracy and other crap he would've had to have put up with daily.
The point I'm getting at is that you need to hire someone that is a good fit for the work, the hours, the environment, who genuinely likes it and loves what they do and doesn't just have a crush on some ideal in their head about your company. This person can rise the the job you give them, they don't have to be an 'A'. And hire what you need. Don't hire young because they are cheap and expendable if you need experienced and well-networked people, and don't hire someone with loads of experience if you can get an entry/junior/mid-level to do the same job and be more motivated, even if they make more mistakes. The best thing that you can do is to spend a lot of time coming up with a good process to hire. Also, do NOT and I really mean do NOT just get some basic programming test off the net and then use that as the interview, and do NOT totally make the candidate feel like an idiot. Both will make people remember your company as "those idiots/bastards who...", which you don't want. Case in point is Google- their interviews were so hard, people didn't even attempt to interview there after hearing about them. That is not good.