I've been using a 520 since October. I started with a 200 in February, and that has never missed a beat. I always knew I'd want to upgrade fairly quickly, and it was a tough decision. Although in many ways the 520 was the least obviously suitable for my needs, I gained the impression from what has been written both here and elsewhere that of all the contenders, the 520 is likely to be the most reliable. Certainly the 810, for similar money, seems much more prone to freezing.
I'm now running the two in parallel, for the moment still using the 200 as the recording and upload device, whilst following my route on the 520. I'll probably switch in the New Year, after which the 200 will be purely backup.
The big inconvenience with the 520 is the lack of a card slot, which means that although you can use open maps to provide satisfactory mapping, you have a limited area of coverage due to the small amount of memory available. If you go elsewhere in the country, you have to remember to swap in a new map before you go and put your normal one back in when you come back. For touring I think this would be a compromise too far.
Having acquired the two units for about £240 in total I reckon I have a good cost-effective setup. I thought the battery life of the 200 was excellent, but the 520 seems even better. It looks as though it will last at least 15 hours when following a route, maybe as much as 24 hours when not. That's with backlight on permanently at 30%, which I find bright enough to be comfortable.
I have little interest in many of the features - live segments for example - but live tracking could be useful one day. If I had my time again I'm not sure I'd make the same decision - either the 1000 and 820 would make my life easier - but for the moment I don't think I'm missing anything other than greater convenience in some areas.
One final thing - I did have a small problem when my planned route was blocked by a road closure, and I had to divert along a road which formed part of my planned route, yet to be ridden, but in the opposite direction. My ride data started updating in fits and starts, but when it did update, it always seemed to be complete. The problem went away once I was out of that situation. Maybe I'll set up a test to see if it happens again.