More care with /bigobj on Windows (#1902)
More care with /bigobj on Windows (#1902)

Expand the set of files to all the imagebufalgo_*.cpp, which are the
most likely files to need it because they tend to have template expansion
for big sets of data type pairings.

FIXME: Does anybody know if there is an advantage to limiting it to
just the files that most need it? Or is it better to make it totally
foolproof by using /bigobj for all our modules on Windows?
lgritz/oiio,OpenImageIO/oiio,lgritz/oiio,OpenImageIO/oiio,lgritz/oiio,OpenImageIO/oiio,lgritz/oiio,OpenImageIO/oiio