I made some tests. Here are my results:
1) reset-settings-2min.jpg - reset all render settings (scene tab > reset settings), then render for 2 minutes - it looks quite ok to me, but I can imagine some flickering in animation, so let's continue:
2) reset-settings-20s.jpg - reset all render settings, then render for 20 seconds. It is easier to see the quality issues now.
3) 20s-givsaa4-lsm1.jpg - lowered gi vs aa to 4, lowered light samples multiplier to 1, then rendered for 20 seconds - as you can see the noise/fireflies are more acceptable now, because we are rendering AA with better quality - there is slight improvement
4) 20s-givsaa4-lsm1-POST.jpg - same as above, but enabled bloom and glare (default settings) and blur+sharpen (default settings) in the vfb - the pixels are additionally blurred
5) 20s-givsaa4-lsm1--CLAMP-POST.jpg - same as above, but enabled highlight clamping in system settings (note: it is NOT the same as "highlight compression" in the vfb!) - all highlights are clamped now, but the quality is much better. It is almost identical to the 2minute rendering. Keep in mind that this will kill the dynamic range of your image, so if you are planning to save to some 32-bit format, then you should not touch highlight clamping. Otherwise, it is perfectly fine to use it, and it can cut down render times dramatically.
Another idea would be to render the image in higher resolution, and then reduce it to the target size. This way the bright highlights would not be smaller than one pixel any more, and it would be easier to sample them more efficiently.
Note: I was using the newest daily build of Corona, where adaptivity is working slightly different, and there is a fix for oversampling dark areas, so results in 1.7 may be a little different. Trying the newest build may be an interesting idea too:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000570015