Target - Field - consistency for release

As i understood it, for the release (and paper), we want the following consistent status (to get rid of the fields keyword at least):

1. one-to-one flagging functions: pass field/target list pairs of equal length to func, and thereby trigger:

`func(field='field1', target='target1')` 
`func(field='field2', target='target2')`
`func(field='field3', target='target3')`
.
.
. 

2. many-to-one (multivariate/cross validating) functions pass a list to field and assign the result functions result to target

I think the idea here, was, to make it so, that, if a function has an own "target" keyword, the machinary would not trigger the standart copy-field-to-target procedure. Currently this is not working. Thats the reason, why still in such a function one would need to

1. assign a dummy field to field - that in addition to being dummy, also has to exist (since it is tried to be copied automatically)

2. use an additional field**s** keyword to pass the actual fields to be included into the calculation

Also, the resulting scores flags-history, will also contain the dummy fields history.

Can that be fixed?