Coding style: import of nested classes

[Gintautas Grigelionis]

In my last PR I tried to address inconsistencies with import of nested
classes, such as Map.Entry; some classes, e.g. IvySettings ended up with
foreach loops over both Entry and Map.Entry. So: should qualified names be
encouraged or avoided?

Gintas